Skip to content

chore(renovate): group Storybook packages so they bump in lockstep#257

Merged
nedtwigg merged 2 commits into
mainfrom
chore/renovate-group-storybook-29297171810
Jul 14, 2026
Merged

chore(renovate): group Storybook packages so they bump in lockstep#257
nedtwigg merged 2 commits into
mainfrom
chore/renovate-group-storybook-29297171810

Conversation

@dormouse-bot

Copy link
Copy Markdown
Collaborator

Problem

Renovate is splitting the Storybook monorepo into one PR per package. The 10.5.0 bump currently opens as three separate, mutually-incompatible PRs — #254 (@storybook/react), #255 (@storybook/react-vite), and #256 (storybook) — and each one alone leaves Storybook in a broken mixed-version state: @storybook/react@10.5.0's preset imports getComponentIdFromEntry from storybook/internal/common, which the 10.4.6 core doesn't export, so the React preset fails to load. storybook build still exits 0 (it only logs Failed to load preset), and the only build-storybook job — Chromatic — is gated on paths: lib/**, so a lockfile-only bump never runs it. The breakage is invisible to CI.

Fix

Add a storybook group so storybook and all @storybook/** packages bump together in a single PR — the same treatment react-router and tailwindcss already get, and for the same stated reason ("framework packages are peered and released together; do not split runtime and build tooling"). Storybook has the identical lockstep property.

Once this merges, Renovate will supersede #254/#255/#256 with one grouped 10.5.0 PR that installs and builds cleanly (verified locally: aligning all three to 10.5.0 removes the preset error).

Details and reproduction are on #255.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jul 14, 2026

Copy link
Copy Markdown

Deploying mouseterm with  Cloudflare Pages  Cloudflare Pages

Latest commit: a061595
Status: ✅  Deploy successful!
Preview URL: https://33970566.mouseterm.pages.dev
Branch Preview URL: https://chore-renovate-group-storybo.mouseterm.pages.dev

View logs

@nedtwigg

Copy link
Copy Markdown
Member

do the same thing for vite and vitest

@dormouse-bot

Copy link
Copy Markdown
Collaborator Author

Done — added a vite group in a061595 covering vite, @vitejs/**, vitest, and @vitest/**. Vitest pins a peer Vite version and the Vite plugins are released against a Vite major, so this keeps a Vite/Vitest peer mismatch from ever landing split across incompatible versions — same lockstep treatment as the storybook, react-router, and tailwindcss groups.

Note: @tailwindcss/vite and @storybook/react-vite stay in their existing groups (vite only matches the package literally named vite, and @vitejs/** doesn't match either), so there's no cross-group overlap.

@nedtwigg nedtwigg merged commit 219d3c4 into main Jul 14, 2026
4 checks passed
@nedtwigg nedtwigg deleted the chore/renovate-group-storybook-29297171810 branch July 14, 2026 20:22
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants